3.11. TC ISCHEDULE

The proposed solution to the “identity crisis” problem was presented; namely webfinger, SCHEDULE-TO-URI and SCHEDULE-ADDRESS property parameter. Lots of discussion about using SCHEDULE-ADDRESS as opposed to setting the routing address as the value of the property. Major pushback for changing the property value is that it may break existing clients which don’t understand SCHEDULE-TO-URIs. The session ended without a clear consensus. The TC will investigate how clients will handle the property value being changed. This will probably wait on IETF to start a Working Group to progress the iSchedule draft, and we will leave it as as open issue in the draft.